Welcome @liangyuanpeng!

It looks like this is your first PR to kubernetes-csi/csi-release-tools 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-csi/csi-release-tools has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

Hi @liangyuanpeng. Thanks for your PR.

I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

/ok-to-test

@msau42 Could you help check whether this image meets the current csi usage requirements? You modified the namespace of the image in the following PR, but it seems that you only want to upgrade the image version?

• Update cloudbuild image #224

/retest
https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-csi_csi-release-tools/278/pull-kubernetes-csi-release-tools-external-provisioner/1930843731896832000

ok  	github.com/kubernetes-csi/external-provisioner/v5/pkg/capacity	26.314s
--- FAIL: TestNodeTopology (60.41s)
    --- FAIL: TestNodeTopology/change-labels (60.00s)
        nodes_test.go:551: unexpected error: get informers in sync: timed out waiting for the condition
FAIL
FAIL	github.com/kubernetes-csi/external-provisioner/v5/pkg/capacity/topology	60.860s

/release-note-none

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liangyuanpeng, xing-yang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

The CVE is fixed. Please rebase.

New changes are detected. LGTM label has been removed.

/retest

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-csi_csi-release-tools/278/pull-kubernetes-csi-release-tools-external-provisioner/1942922407836651520

  STEP: Destroying namespace "volume-expand-7977" for this suite. @ 07/09/25 13:00:22.832
  << Timeline
  [FAILED] While waiting for pvc to have fs resizing condition: error waiting for pvc "hostpath.csi.k8s.iojtcqb" to have filesystem resize status: error fetching pvc "hostpath.csi.k8s.iojtcqb" for checking for resize status : client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
  In [It] at: k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:238 @ 07/09/25 13:00:17.596

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-csi_csi-release-tools/278/pull-kubernetes-csi-release-tools-external-snapshotter/1942922407933120512

...
go: download go1.23.3: golang.org/[email protected]: read "https://proxy.golang.org/golang.org/toolchain/@v/v0.0.1-go1.23.3.linux-amd64.zip": write /home/prow/go/pkg/mod/cache/download/golang.org/toolchain/@v/v0.0.1-go1.23.3.linux-amd64.zip112168608.tmp: 
no space left on device
ERROR: Please install Go 1.21+
WARNING: E2E parallel features failed

/retest

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-csi_csi-release-tools/278/pull-kubernetes-csi-release-tools-external-provisioner/1942962664179240960

WARNING: DATA RACE
Read at 0x00c0005cd380 by goroutine 233:

Seems like it's using csi-release-tools master for jobs of pull-kubernetes-csi-release-tools-external-provisioner and pull-kubernetes-csi-release-tools-external-snapshotter , so it's not releated with this PR, right?

@gnufied I see that you have opened a PR: kubernetes/test-infra#35116 for this case, could you please confirm that? thanks.

/retest

@liangyuanpeng: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.